Going-Live Checklist

Here is the criteria that we will use to test a customer’s implementation before approving them to go live in production using the API.

User identification

• Unique users are properly tracked across multiple devices as client_id.
• Users are tracked according to their payment plan/business model.

Basic Content Viewer Flow

• Invokes /app-start when app starts.
• Invokes /music-check or /music-fetch before playback.
• Invokes /play when playback begins.
• Invokes /app-close when app closes.
• Correctly handles tracks that have been taken down.
• Client ID follows user across devices.
• Offline playback is handled correctly by one of the following patterns:
  • streaming is prevented when /play fails due to networking.
  • streaming continues and /play is invoked in the future with a back-dated timestamp.

Content Creator Flow

• Previewing clips invokes /play with preview=true.
• Create a custom clip:
  • User may not listen to the full track uninterrupted.
  • Custom clips cannot exceed 60s in length.
• Previewing a track while making a custom clip invokes /track-play.
• Apps in non-US + territory markets: graceful UX blocking access to the API.
• Adding a clip to content:
  • No more than one clip is able to be added to media.
  • Ensure it plays after being posted (if applicable).
• Sharing to a 3rd party works as expected, invoking /share.
• Downloading works as expected, invokes /download.

Licensing Requirements

• Artist, album, track appears during playback.
• End User Licensing Agreement is Updated with Feed Terms.
• Feed Clips are not accessible outside the US & its territories.
• If applicable, test that Content ID passes and fails as expected.
  • Track in the background is in our catalog: pass.
  • Track in the background and we can’t match it to anything: pass.
  • Track in the background isn’t in our catalog: blocked.

Confirmation of Prod Credentials

• Ensure production API credentials (not development) are used after going live.